-
Notifications
You must be signed in to change notification settings - Fork 3.2k
feat(ingestion/snaplogic): Add snaplogic as a source for metadata ingestion #14231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
feat(ingestion/snaplogic): Add snaplogic as a source for metadata ingestion #14231
Conversation
b93e74e to
c492535
Compare
Bundle ReportChanges will increase total bundle size by 6.08kB (0.02%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: datahub-react-web-esmAssets Changed:
Files in
|
c492535 to
b434b4a
Compare
|
Thanks for the contrib @SalimAbdul-snaplogic -
thanks! |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
|
Hello, thanks for raising the PR! Seems like there's failing lint. could you run this and push the changes? It should auto-fix most issues, but a few may need to be fixed manually. you can locally validate lint by this command : @treff7es could you review this PR? thanks! |
1163b0f to
7e19d72
Compare
Thank you. |
|
Hi @treff7es Need your help with review here. Please let us know if any questions. |
Add new source for metadata ingestion.
In this PR I'm adding basic functionality to harvest lineage from snaplogic to datahub.
Mainly we want to load column/table level lineages. Apart from that we're mapping snaplogic pipeline to datahub pipeline.
Snaplogic pipeline is a big pipeline that contains a lot of small operations. So we create one Pipeline in the datahub that contains a lot of small tasks. Mapping is described in the generated documentation.
What we're not mapping: Snaplogic task and plex.
Currently we don't see performance issues but we will be testing this implementation on heavy loaded envs later.